This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
ran yesterday into a reproducible problem with the Split function:
<code>
s="##"
uName$="name"
uCompany$="company"
adr_adr1$="adr_adr1"
adr_adr2$="adr_adr2"
adr_nop$="adr_nop"
ucity$="city"
pays$="" '<-empty !!
adr_tel1$="tel1"
uEmail$="Email" adr_fax2$="4711"
adr_dep$="la la la la"
adr_no$="1234"
updatefields={SET "name"=[1]
SET "company"=[2]
SET "Address"=[3]
SET "Apt./Suite"=[4]
SET "zip"=[5]
SET "city"=[6]
SET "Addr Intl"=[7]
SET "Pax Office Phone"=[8]
SET "Pax Email"=[9]
SET "Pax Office Fax"=[10]
SET "state"=[11]
SET "Employee Number"=[12]}
For i%=0 To Ubound(updatefields)
Print updatefields(i%)
Next
<\code>
Because of 1 empty entry we get the situation that 2 separators "####" can be found in the string and Split is not able to handle it.
We got results like this :
...SET "Employee Number"=[12]namecompanyadr_adr1adr_adr2adr_nopcity##tel1##Email##4711##la la la la##1234#tel1##Email##4711##la la la la##1234tel1Email4711la la la la1234
Exactly at the point where there were two separators but no value between them, Split started to become messy.
Joe
Feedback number WEBB87BDRV created by ~Evelyn Lopveluplopings on 07/13/2010
Status: Open
Comments: